54%

4.3.10.a Recurrence Rule

15

0

2

2

19

79%

Only use first instance. No errors for incorrect data

4.3.10.b Recurrence Rule

15

0

2

2

19

79%

No errors for incorrect data. Some do not support ‘SECONDLY’ / ‘MINUTELY’ / ‘HOURLY’ frequences

4.3.10.c Recurrence Rule

8

5

4

2

19

42%

Issues related to use of timezones in UNTIL: some only handle UTC. One does DATE only not DATETIME in UNTIL. One does not export UNTIL any longer due to legacy and server compatibility issues, but attempts to read UNTIL as best it can.

4.3.10.d Recurrence Rule

12

3

2

2

19

63%

BYSETPOS not fully supported. No errors for incorrect data.

4.6.1.a Event Component

15

0

1

2

18

83%

Some PROPS not stored, Only last value used if specified more than once. One vendor does not export geo and url.

4.6.1.b Event Component

12

0

4

2

18

67%

Some do not support EXRULE, RDATE etc. Some PROPs not stored. Only first instance of PROP used. One does not export comment, exrule, rstatus, and related. Some only support zero or one RRULE, and no exrules.

4.6.2.a To-do Component

11

3

2

2

18

61%

Some do not support TODO. Some PROPS not stored.

4.6.2.b To-do Component

9

3

4

2

18

50%

Some do not support EXRULE, RDATE etc. Some do not support TODO. Some PROPs not stored. Only first instance of PROP used. Some do not support RRULE and EXRULE for VTODO.

4.6.3.a Journal Component

4

7

5

2

18

22%

Most do not generate VJOURNAL. Some consume it. Some ignore it.

4.6.3.b Journal Component

3

9

3

2

17

18%

Most do not generate VJOURNAL. Some consume it. Some ignore it.

4.6.4.a Free/Busy Component

10

4

2

2

18

56%

Some do not support VFREEBUSY. Some issues with timezones. One only imports and exports with the Internet Free Busy feature. Some ignore it.

4.6.5.a Time Zone Component

10

5

1

2

18

56%

Some only use UTC.

4.6.5.b Time Zone Component

10

5

1

2

18

56%

Some only use UTC. One always exports UTC or Floating time if possible, but can import iCals which use this area of the spec.

4.6.5.c Time Zone Component

9

4

2

2

17

53%

Some only use UTC.

4.6.6.a Alarm Component

9

6

1

2

18

50%

Some do not support VALARM. Some do not support repeating alarms. Some support sending alarm components.

4.6.6.b Alarm Component

7

7

2

2

18

39%

Some do not support VALARM. Some do not support repeating alarms.

4.6.6.c Alarm Component

6

5

4

2

17

35%

Some do not support VALARM. Some do not support repeating alarms.

4.8.4.4.a Recurrence ID

11

2

2

2

17

65%

Some do not implement. Some produce just the date portion for RECURRRENCE-ID; no Time and do not set DATE parameter.

4.8.4.4.b Recurrence ID

10

2

3

2

17

59%

Some do not implement. Some do not handle more than one R-ID. Some do not import/export DATE-TIME or rangeparam.

4.8.4.4.c Recurrence ID

6

4

5

2

17

35%

Some do not support XPARAMS. One only reads first XPARAM.

4.8.5.1.a Exception Date/Times

11

1

2

2

16

69%

One changes start date of instance.

4.8.5.1.b Exception Date/Times

11

2

1

2

16

69%

Some do not implement. One does not export DATE-TIME since that’s implicit.

4.8.5.1.c Exception Date/Times

5

6

4

2

17

29%

Some ignore XPARAMs on EXDATE.

4.8.5.3.a Recurrence Date/Times

9

3

2

2

16

56%

One does not implement RDATE only RRULE. Some do not support VALUE=PERIOD for EXDATEs or RDATEs.

4.8.5.3.b Recurrence Date/Times

6

5

4

2

17

35%

One does not implement RDATE only RRULE. Some do not support XPARAMs

4.8.5.4.a Recurrence Rule

9

3

4

2

18

50%

Some do not support RDATE. Some generate new components if component changed. Some use EXDATE to detach instances. Some do not support PERIOD in RDATEs.

4.8.7.4.a Sequence Number

7

3

5

2

17

41%

One changes SEQUENCE when other PROPs change. Some require new event for change. Some do not increment sequence of instance when start or end of instance is changed.

18%

3.2.4.a VEVENTCANCEL

9

4

2

2

17

53%

Some do not support. One generates OK, but does not consume it OK.

3.2.4.b VEVENTCANCEL

6

7

2

2

17

35%

Some do not support. One generates OK, but does not consume it OK. Some use EXDATE for cancellations.

3.2.4.c VEVENTCANCEL

2

8

5

2

17

12%

Some do not support. One generates OK, but does not consume it OK. Some use EXDATE for cancellations. Some only handle single instance or the entire set. Some do not support RANGE in RECURRENCE-ID.

3.4.5.a VTODOCANCEL

3

9

3

2

17

18%

Some do not support. Some do not support iTIP + VTODO. One generates OK, but does not consume it OK.

3.4.5.b VTODOCANCEL

3

9

3

2

17

18%

Some do not support. Some do not support iTIP + VTODO. One generates OK, but does not consume it OK.

3.4.6.a VTODOREFRESH

1

10

3

2

16

6%

Some do not support. Some do not support iTIP + VTODO. One generates OK, but does not consume it OK.

3.5.3.a VJOURNALCANCEL

1

10

3

2

16

6%

Some do not support. Some do not support iTIP + VJOURNAL.

3.5.3.b VJOURNALCANCEL

0

11

3

2

16

0%

Some do not support. Some do not support iTIP + VJOURNAL.

See Clause 2 tab

See Clause 3 tab